test: Add tests for parsing logs from init commands, tests for parsing of RFC3339 timestamps with different levels of precision #180
+175
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue
N/A
Description
In hashicorp/terraform#34886
initcommands were given some support for JSON output using the-jsonflag. Log messages from the init command are a mixture of types"log"and"init_output".This PR adds some tests showing the current behaviour of how JSON logs from init are parsed. Currently terraform-json doesn't recognise the
init_outputtype of log, so those logs are parsed as an unknown message type.Also, this PR's test was made using output generated from Terraform using the code from PR hashicorp/terraform#37818. This demonstrates that parsing JSON logs is unaffected by that change, but just to be sure I added a test that generates timestamps in both formats and shows that both are parsed fine (though there are different levels of precision, expectedly).
Rollback Plan
Changes to Security Controls
N/A